We have a SBS 2011 server with Exchange 2010 with SP2 + update rollup 4 installed. Some of our clients are getting the follwing synchronisation errors (server errors) in Outlook (2007): [80004005-501-FFFFF9BB-324] When they add an appointment to their calender in Outlook or on their mobile phone, these appointments aren't synchronised to the Exchange server. We tried creating new Outlook profiles, using scanost on the clients but the errors come back. This server was reinstalled after it woudn't boot anymore, we then restored the systemstate, after this these problemens appeared. Can anyone tell me what the above error message means, I can't find anything about it.

Hi, What is the error recorded in the server side? How does the client connect to Exchange server? internally in LAN or externally via Outlook Anywhere? Are you getting the error for shared calendar synchronisation? For the error message, it is reported by Outlook, so I'd suggest you post this question in Outlook forum at the same time. Your understanding would be appreciated. Fiona Liao TechNet Community Support

Clients connect internally in LAN, no shared calenders. Sorry they were actual local errors, I fixed the synchronisation issues by exporting the users mailbox, then disconnected their mailboxes and create new mailboxes, then importing everything back in again. I got some error messages along the way saing some items were corrupted, probably this caused the problems? After this is ran a New-MailboxRepairRequest against the database, this fixed some more corruptions in the database. Are there more things we can do to check the database for corruption?

Clients connect internally in LAN, no shared calenders. Sorry they were actual local errors, I fixed the synchronisation issues by exporting the users mailbox, then disconnected their mailboxes and create new mailboxes, then importing everything back in again. I got some error messages along the way saing some items were corrupted, probably this caused the problems? After this is ran a New-MailboxRepairRequest against the database, this fixed some more corruptions in the database. Are there more things we can do to check the database for corruption?

I'm going to check this out, thanks.

Not at mailbox item level. We may use Exchange performance monitor, or the cmdlets below: Get-MailboxDatabase Get-MailboxStatistics Get-StoreUsageStatistics Refer to: http://technet.microsoft.com/en-us/library/ff367871.aspx http://social.technet.microsoft.com/wiki/contents/articles/2335.aspx (for Exchange 2007)Fiona Liao TechNet Community Support